PVC/Adapter Description

The virtual circuit and logical adapter description fields hold 20 character text strings that provide useful information about these items. This field is optional and is used for reference when configuring or monitoring PVCs and logical adapters.


Virtual Circuits Properties

The virtual circuits property page configures virtual circuits and logical adapters. Logical adapters are groups of virtual circuits that appear as a single network adapter. If you define multiple logical adapters, each logical adapter is treated as a separate network adapter.

The left side of the page is a tree control that shows all configured logical adapters and all virtual circuits assigned to each logical adapter. To configure a logical adapter or virtual circuit, click on the item in the tree control with the left mouse button. All configurable settings for the item will be displayed to the right of the tree control. Only the settings that are commonly set by the user are displayed by default. To display advanced settings for an item click on the Show Advanced button. Modification of the advanced settings is rarely necessary. Before changing any advanced settings, be sure you are familiar with the function of the setting.

To view the virtual circuits assigned to a logical adapter click the left mouse button on the plus “+” sign to the left of the adapter item icon, in the tree control. This will expand the branch of the tree control that contains the assigned virtual circuits.

Adding a New Logical Adapter

To add a new logical adapter item click on the New Item button. Select an item type of logical adapter when prompted and click OK. The new logical adapter should now appear in the tree control. You can also click any place in the tree control with the right mouse button to reveal a pop-up menu that allows you to add a new item.

Adding a New Virtual Circuit

To add a new virtual circuit to a logical adapter, select the logical adapter in the tree control and click on the New Item button. Select an item type of virtual circuit when prompted and click OK. Enter the DLCI (Data Link Connection Identifier) of the virtual circuit when prompted. The DLCI is assigned by the network provider at subscription time. Click OK to finish adding the virtual circuit. The virtual circuit should now appear in the tree control as a member of the selected logical adapter.

Logical Adapter Properties

Each virtual adapter has the following properties:

Description

Network Protocols

MAC Address (Advanced)

Virtual Circuit Properties

Each virtual circuit has the following configurable properties:

Description

Data Link Connection Identifier (DLCI)

Committed Information Rate (CIR)

Extended Information Rate (EIR)

Advanced Settings

Removing Logical Adapters or Virtual Circuits

To remove an item, select the item in the tree control and click on the Remove Item button. You will be prompted for confirmation before deleting the item.

WARNING:

Once an item is deleted, ALL configuration information for that item is lost! If you delete a logical adapter, ALL virtual circuits assigned to that logical adapter are also deleted!


CIR, Committed Information Rate

The committed information rate (specified in bits per second) is used to control the rate data is sent on the virtual circuit.

The CIR is set at subscription time in agreement with your network provider. The CIR is the amount of data guaranteed to be carried by the network during normal operating conditions. The virtual circuit can send data in excess of the CIR (bursting) as allowed by the Excess Information Rate (EIR).

When the CIR is set to zero then the SyncLink adapter sends data on the virtual circuit as fast as possible (up to the access port data rate) without regard for network congestion. If network congestion occurs, the data in excess of the CIR may be discarded. Any lost data should be retransmitted by the higher level protocols (IP, IPX, etc.). This is the default setting.

When the CIR is set to a non-zero value, the data rate for the PVC will be reduces to the CIR during network congestion. When no network congestion exists, data will be sent on the PVC in excess of the CIR as allowed by the EIR setting.


EIR, Excess Information Rate

The excess information rate (EIR) is used to control the data rate of a virtual circuit when no network congestion exists. The EIR specifies the data rate (in bits per second) in excess of the Committed Information Rate (CIR) to which a virtual circuit can burst when no network congestion exists.

If the EIR is set to zero (disabled), a virtual circuit will burst up to the full access port data rate, when there is no network congestion. When network congestion exists, the virtual circuit data rate is throttled to the CIR. This is the default setting.

If the EIR is non-zero, the virtual circuit will burst up to CIR+EIR when there is no network congestion. When network congestion exists, the virtual circuit data rate is throttled to the CIR.


Advanced PVC Settings

Network to Hardware Address Mapping

Each virtual circuit is a connection between the local computer and a remote computer. Multiple virtual circuits can be grouped into a logical adapter. All virtual circuits on a logical adapter share a common network address (IP) or network number (IPX). The operating system sends a packet to a remote computer by submitting the packet to the logical adapter that shares the network address of the remote computer.

The logical adapter must determine on which virtual circuit to send the packet. This is done by examining the host address (IP) or node address (IPX) of the packet and mapping this address to a hardware (MAC) address. The MAC address identifies which PVC to use.

The Address Resolution Protocol (ARP) and Inverse ARP (IARP) are protocols used to dynamically map network addresses (such as an IP or IPX address) to a hardware address (such as the frame relay DLCI).

Inverse Arp Enabled

The SyncLink adapter always processes incoming ARP and IARP requests and responses from a remote computer. The SyncLink adapter, by default, sends ARP requests to determine the address mapping of a remote station. If Inverse ARP Enabled is checked, the SyncLink adapter will send IARP requests instead.

The default setting should work with most equipment (router or computer). If the remote equipment does not respond to ARP requests but does respond to IARP requests, enable (check) this setting. If you are not sure then leave this setting in the default (disabled) state.

Remote IP and IPX Addresses

The remote IP and IPX address fields manually map network addresses to the selected virtual circuit. This is usually done automatically with the ARP and Inverse ARP protocols, in which case these fields can be left blank. If the SyncLink adapter must communicate with hardware from another vendor that does not support the ARP or Inverse ARP protocols, it is necessary to enter the network address of the remote computer or router. It is only necessary to enter the network addresses for network protocols that are enabled. If there is only one virtual circuit defined for the selected logical adapter, these fields can be left blank.


Network Protocols

Each logical adapter and all of the associated virtual circuits can be configured to use one or more network protocols (Routed IP, Routed IPX, and Bridging). The network protocol necessary for a given installation is application dependent. Consult with your network administrator for which network protocol(s) will be necessary.

The routed IP protocol is used for communicating with the internet and for many large enterprise networks. When using the SyncLink adapter to communicate with routers and other SyncLink adapters using IP, check this box. This is the most common protocol, and is enabled by default.

The routed IPX protocol is used in Netware environments. When using the SyncLink adapter to communicate with routers and other SyncLink adapters using IPX, check this box. This is disabled by default.

Bridging enables encapsulation of entire Ethernet packets into frame-relay frames for transport to a remote location. This allows the use of non-routed protocols and protocols that are not directly convertable to frame-relay frames such as NetBEUI. If the SyncLink is communicating with a third party Ethernet bridge then check this box.

The SyncLink adapter can simultaneously carry routed IP, routed IPX, and bridged network traffic.


MAC Address

This parameter is automatically assigned and should not be changed unless necessary.

The Media Access Control (MAC) Address is the hardware address associated with a network adapter. The hardware address is used to transfer data on the physical media (such as Ethernet or Frame Relay) and is different for each media type.

When transferring data using a network protocol such as IP or IPX, the host computer uses a protocol address. For example, an IP address of 205.4.23.13 or an IPX address of 3002.4534FEB402C1. The network hardware uses only MAC addresses and does not recognize protocol addresses. The host computer maps (translates) the protocol address to a hardware address (MAC address) before giving a packet to the hardware for transmission. When a packet is received from the network adapter, the host computer maps the MAC address back to a protocol address.

The mapping of MAC addresses to protocol addresses can be handled automatically by the SyncLink adapter using the ARP and Inverse ARP protocols. When communicating with hardware from other vendors that do not support these protocols, the address mapping must be entered manually.


Configuring the Serial Interface

The SyncLink adapter is shipped with one of its three serial interfaces pre-configured.  The serial interface is configured by placing the 17-position jumper on one of three jumper blocks (J5, J6, J7).  The jumper is placed so as to completely cover one of the jumper blocks.  If necessary, the serial interface can be changed by moving the jumper to the desired block.

To configure the serial interface of the SyncLink adapter, follow the steps outlined below.

1.	For convenience of jumper removal, a combination of two black 8-pin jumpers separated by a single-pin colored jumper is used to form the 17-position interface jumper.

NOTE:  The 8-pin jumpers are installed with the shorting bars visible on top.  This orientation MUST be maintained when relocating.

2.	Removal of the interface jumper is accomplished by first removing the colored jumper, then the black 8-pin jumpers one at a time using common pliers.

NOTE:  DO NOT  attempt removal with a screwdriver, needle-nose pliers, or any tool other than pliers.  This may cause damage to the jumper, the jumper block pins, or the board.

3.	Holding the SyncLink in one hand with the component side up, grasp the 8-pin jumper firmly about the middle with the pliers and gently remove it by applying sufficient perpendicular force away from the board.  The jumper should come off easily.

4.	Insert the jumpers by hand onto the corresponding pins of the desired interface jumper block with the shorting bars on top and push down firmly.

Electrical Interface

RS-232 Interface

Jumper J5 (ISA) or J1 (PCI) selects the RS-232 serial standard. This uses V.28 single-ended drivers and receivers for all signals and a DB-25 connector. This setting is used for connecting to slow speed serial devices such as modems.

V.35 Interface

Jumper J6 (ISA) or J2 (PCI) selects the V.35 serial standard. This uses V.11 differential drivers and receivers for data and clock signals. V.28 single ended drivers and receivers are used for the remainder of the serial signals. The SyncLink V.35 pinout may be used for direct connection to a DCE that implements the Codex V.35 pinout for a DB-25 connector. For DCE devices that use the ISO-2593 34-pin Block Connector, an adapter cable is required (available from MicroGate Corporation).

RS-422 Interface

Jumper J7 (ISA) or J3 (PCI) selects the RS-422 serial standard. This uses V.11 differential drivers and receivers for all serial signals. This standard is capable of data rates up to 10 Mbps. The SyncLink adapter supports the RS-530 standard for serial connector pinout through a DB-25 interface (no adapter cable required). RS-449 uses the same electrical specification as RS-530, but uses a DB-37 connector, so an adapter cable is required (available from MicroGate Corporation).

Data Port Signals.2 Data Port Signals.2 Data Port Signals.2 Data Port Signals (DB-25 Pin Serial Connector)

Tables 1, 2, and 3 give signal names and pinouts for the data port's RS-232, V.35, and RS-422 serial interfaces, respectively.

Table 1: RS-232 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 Pin No.
Earth Ground		1
Signal Ground		7
RTS	RS-232/V.28	4
CTS	RS-232/V.28	5
DTR	RS-232/V.28	20
DSR	RS-232/V.28	6
DCD	RS-232/V.28	8
RI (Ring)	RS-232/V.28	22
TxD	RS-232/V.28	2
RxD	RS-232/V.28	3
TxCLK	RS-232/V.28	15
RxCLK	RS-232/V.28	17
AuxCLK	RS-232/V.28	24

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output

Table 2: V.35 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 Pin No.	V.35 Block Pin No.
Earth Ground		1	A
Signal Ground		7	B
RTS	RS-232/V.28	4	C
CTS	RS-232/V.28	5	D
DTR	RS-232/V.28	20	H
DSR	RS-232/V.28	6	E
DCD	RS-232/V.28	8	F
RI (Ring)	RS-232/V.28	22	---
TxD+	RS-422/V.11	2	P
TxD-	RS-422/V.11	14	S
RxD+	RS-422/V.11	3	R
RxD-	RS-424/V.11	16	T
TxCLK+	RS-422/V.11	15	Y
TxCLK-	RS-422/V.11	13	AA
RxCLK+	RS-422/V.11	17	V
RxCLK-	RS-422/V.11	19	X
AuxCLK+	RS-422/V.11	24	U
AuxCLK-	RS-422/V.11	23	W

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output

Table 3: RS-422 Data Port Pin Connections

Signal Name	Electrical Desc	DB-25 (RS-530) Pin No.	DB-37(RS-449) Pin No.
Earth Ground		1	1
Signal Ground		7	19
RTS+	RS-422/V.11	4	7
RTS-	RS-422/V.11	19	25
CTS+	RS-422/V.11	5	9
CTS-	RS-422/V.11	13	27
DTR+	RS-422/V.11	20	12
DTR-	RS-422/V.11	23	30
DSR+	RS-422/V.11	6	11
DSR-	RS-422/V.11	22	29
DCD+	RS-422/V.11	8	13
DCD-	RS-422/V.11	10	31
TxD+	RS-422/V.11	2	4
TxD-	RS-422/V.11	14	22
RxD+	RS-422/V.11	3	6
RxD-	RS-424/V.11	16	24
TxCLK+	RS-422/V.11	15	5
TxCLK-	RS-422/V.11	12	23
RxCLK+	RS-422/V.11	17	8
RxCLK-	RS-422/V.11	9	26
AuxCLK+	RS-422/V.11	24	17
AuxCLK-	RS-422/V.11	11	35

NOTES:

<Signal Name>+ represents the inverting input/output

<Signal Name>- represents the non-inverting input/output


Diagnostics

When the SyncLink driver starts, it tests the adapter and posts problems to the event log with a source name of MGFR. View the event log with the event viewer in Administrative Tools. Refer to the Windows documentation for information on using the event viewer.

The Diagnostics property page of the adapter property sheet displays the current startup status of the device. Errors are displayed on this page as well as in the event log. If no errors are detected, a data loopback test can be performed:

1.	Select the Internal Loopback or External Loopback data test mode.

NOTE:  An external loopback connector is required for the external loopback test. Without the loopback connector, the external diagnostics will fail. The proper interface loopback connector is supplied with the card.  The serial interface of the SyncLink adapter must be configured to match the interface labeled on the loopback connector (RS-232/V.35 or RS-422).  For more information on the serial interface, refer to section Configuring the Serial Interface.

2.	Click the Start Test button to begin testing.  Diagnostics will loop data through the card.  If an error occurs, a message will be displayed and the test will continue.

1.	Click on the Stop Test button to end the test and display the test results.

The frame relay monitor program can be used to verify adapter operation in normal use.


Hardware Settings

These settings are located in the Hardware property page of the SyncLink Frame Relay Adapter property sheet.

Also see Resources.

Access Port Data Rate

The access port data rate is the speed in bits per second (bps) in which data is transferred over the physical serial port that connects the SyncLink adapter to the communications device (CSU/DSU, Modem, etc.).

These are examples of the access port data:

V.34 Modem	28800bps

Leased DDS I CSU/DSU	56000bps

Bonded ISDN (2 B-Channels)	128000bps

T-1 CSU/DSU	1544000bps

Incorrectly setting this parameter could result in incorrect network timeouts.

Generate Clock

The data clocks are usually provided by the attached modem or CSU/DSU. In rare instances, it may be necessary for the adapter to generate these clocks. Enable this check box if the adapter needs to generate the data clocks. The clock signal is output on the AUXCLK serial signal. Depending on the application, external cabling may be necessary to route the AUXCLK signals to the correct RCLK and TCLK signals.

PVC Management Protocol

The PVC management protocol controls and monitors the virtual circuits on a frame relay connection. The type of protocol is specified by your network provider at subscription time. The most common protocol in the U.S. is ANSI T1.617 Annex D, which is sometimes referred to as simply Annex D. In Europe, a common protocol is Q.922 Annex A or just Annex A. The default protocol is Annex D.

Restart Device

Clicking the restart device button forces the driver to stop, reread the configuration, and restart. This is necessary when changes are made to the network settings for the adapter.


NULL Modem

A Synchronous NULL Modem is a simple device which connects two DTE communications devices to each other, without using a modem or CSU/DSU. The NULL modem is placed between the two adapters.

Data Clocks

A NULL modem for synchronous communication is different from a NULL modem used for asynchronous communication. Synchronous communication uses clock signals, which MUST be supplied to both adapters. Usually the attached communications device (modem or CSU/DSU) provides the data clocks. When using a NULL modem, one of the adapters must be set to provide external clocks. The SyncLink adapter can provide a clock source on the AUX Clock pin of the serial interface. This is controlled in the Adapter Settings property page of the SyncLink SDLC Link Service setup. The NULL modem routes this clock output to the transmit and receive clock inputs on both adapters. This means the NULL modem must be attached with the Clock Source end to the SyncLink adapter that is supplying the external clock signal.

NULL Modem Wiring

The exact wiring of the NULL modem will depend on the serial interface configuration of the SyncLink adapter: RS-232, V.35, or RS-530.

The following NULL modem cabling requirements are necessary for use with the SyncLink adapter:

RS-232 Null Modem

Clock Source End

DSR (Pin 6)	DTR (Pin 20)

DCD (Pin 8)	RTS, CTS (Pins 4,5)

DTR (Pin 20)	DSR (Pin 6)

RTS, CTS (Pins 4,5)	DCD (Pin 8)

Tx Clock, RxClock, AUX Clock 	TxClock,Rx Clock

(Pins 15,17,24)	(Pin 15,17)

Transmit Data[TxD] (Pin 2)	Receive Data[RxD] (Pin 3)

Receive Data[RxD] (Pin 3)	Transmit Data[TxD] (Pin 2)

V.35 Null Modem

The V.35 NULL modem is similar to the RS-232 NULL modem, except the data and clock signals use two wires each. In this table, each signal pair is described by <Signal Name>+ and <SignalName>-.

Clock Source End

DSR (Pin 6)	DTR (Pin 20)

DCD (Pin 8)	RTS, CTS (Pins 4,5)

DTR (Pin 20)	DSR (Pin 6)

RTS, CTS (Pins 4,5)	DCD (Pin 8)

Tx Clock+, RxClock+, AUX Clock+	TxClock+, Rx Clock+

(Pins 15,17,24) 	(Pins 15,17)

Tx Clock-, RxClock-, AUX Clock- 	TxClock-, Rx Clock-

(Pins 13,19,23)	(Pin 13,19)

Transmit Data[TxD+] (Pin 2)	Receive Data[RxD+] (Pin 3)

Transmit Data[TxD-] (Pin 14)	Receive Data[RxD-] (Pin 16)

Receive Data[RxD+] (Pin 3)	Transmit Data[TxD+] (Pin 2)

Receive Data[RxD-] (Pin 16)	Transmit Data[TxD-] (Pin 14)

RS-530 Null Modem

The RS-530 NULL modem uses two wires per serial signal. In this table, each signal pair is described by <Signal Name>+ and <SignalName>-.

Clock Source End

DSR+ (Pin 6)	DTR+ (Pin 20)

DSR- (Pin 22)	DTR- (Pin 23)

DCD+ (Pin 8)	RTS+,CTS+ (Pins 4,5)

DCD- (Pin 10)	RTS-,CTS- (Pins 19,13)

DTR+ (Pin 20)	DSR+ (Pin 6)

DTR- (Pin 23)	DSR- (Pin 22)

RTS+,CTS+ (Pins 4,5)	DCD+ (Pin 8)

RTS-,CTS- (Pins 19,13)	DCD- (Pin 10)

Tx Clock+, RxClock+, AUX Clock+ 	TxClock+,Rx Clock+

(Pins 15,17,24)	(Pins 15,17)

Tx Clock-, RxClock-, AUX Clock- 	TxClock-,Rx Clock-

(Pins 12,9,11)	(Pins 12,9)

Transmit Data[TxD+] (Pin 2)	Receive Data[RxD+] (Pin 3)

Transmit Data[TxD-] (Pin 14)	Receive Data[RxD-] (Pin 16)

Receive Data[RxD+] (Pin 3)	Transmit Data[TxD+] (Pin 2)

Receive Data[RxD-] (Pin 16)	Transmit Data[TxD-] (Pin 14)


Frame Relay Overview

Frame Relay is a packet switching technology that allows a user to communicate with multiple endpoints (other users) using a single physical access port (serial port) connected to a common public network (also called the cloud) which consists of network switches that transport and route packets between endpoints. The interface between the user equipment and the network is called the User-Network Interface (UNI). The network capacity (bandwidth) is shared by all subscribers (users).

Frame Relay communications is independent of a particular physical media and is commonly run over leased 56K DDS, FT1/T1 and T3 circuits.

Data is framed using bit synchronous HDLC with NRZ encoding. The frame contains a Data Link Connection Identifier (DLCI) which specifies a logical link, called a Virtual Circuit, between endpoints. The SyncLink adapter supports Permanent Virtual Circuits (PVC), where the endpoints connected by the virtual circuit are predetermined at subscription time in agreement with the network provider.

The network uses the DLCI of a frame submitted to the network by a user to determine which endpoint receives the frame. When a frame is received by the user from the network, the origin of the frame can be determined by the user from the DLCI. The same virtual circuit can be identified at the two endpoints by two different DLCIs. This is because the DLCI only has local significance. This routing of data on a per packet basis within the network is what allows a single access port to communicate with multiple endpoints.

The following illustration shows three stations connected through a frame relay network. Two PVCs are represented. Station A is connected to Station B through a PVC. Station A identifies this PVC with DLCI 17 while station B identifies the same PVC with DLCI 18. This demonstrates how a single PVC can be known by different DLCIs, where each DLCI has only local significance (to a particular endpoint). Station A is also connected to Station C with another PVC. In this case each endpoint identifies the PVC with the same DLCI (16). This is acceptable because, as stated above, the DLCI has only local significance. The PVC connections inside the frame relay network are drawn for clarity. The actual internal structure of the network is not known and may consist of multiple interconnected network switches.

When there is a large volume of data traffic, the network may not have adequate capacity to carry all frames causing a condition known as congestion. In this case, frames may be discarded by the network, therefore, all protocols operating over frame relay must implement their own form of error detection and recovery.

The committed information rate (CIR) is the amount of data the network provider guaranties to transfer under normal network conditions. In extreme conditions, frames transmitted within the CIR may still be discarded, but in most cases, the data will be successfully transported. The CIR value can range from 0 up to the data rate of the access port.

The excess information rate (EIR) is the amount of data in excess of the CIR that can be transferred. Normally when no congestion exists, a PVC will burst up to the access port data rate. The amount of bandwidth used by a PVC can be limited in non-congestion situations by setting the EIR such that the CIR+EIR is less than the access port data rate.

The network attempts to avoid discarding frames by using congestion management. Each frame carries information about network congestion. The SyncLink adapter monitors the Backward Explicit Congestion Notification (BECN) bit. If a frame is received with the BECN bit set, congestion exists in the network. In this case, the SyncLink reduces the data rate to the configured CIR. The network attempts to inform the user of congestion before any frames are discarded. The user should reduce bandwidth consumption to alleviate the congestion and avoid dropped frames. However, it is not guaranteed that the user will receive notification of congestion before frames are discarded.


Data Encapsulation

Frame relay can support the transport of many standard protocols using the IETF RFC1490 standard for multiprotocol encapsulation over frame relay. RFC1490 describes a method of encapsulation that involves adding fields in the HDLC frame information field that precedes the actual user data (the protocol and data being encapsulated).

Virtual Circuit Management

In addition to transferring user data, the user equipment and the network use a message passing protocol to manage virtual circuits. The messages use the standard frame relay framing and are exchanged using a management DLCI (DLCI 0 or DLCI 1023).  Management DLCIs are in the reserved range of DLCIs and so cannot be confused with user data. Since the management messages are exchanged on the same physical link as the user data, the management procedures are called in-band signaling. By exchanging management messages with the network, the user can determine the presence and state of PVCs and verify the correct operation of the network. The network uses the management protocol to verify the correct operation of the attached user device.

The core procedures for managing PVCs involves periodic polling of the network by the user equipment. The user sends a Status Enquiry message at a regular interval to the network. The network responds to the Status Enquiry message with a Status message. The Status message contains information about which PVCs are present and if the PVCs are available for use. The user monitors the PVC status information portion of the status message to determine if data can be exchanged on a particular PVC. The network is also allowed to send Status messages asynchronously (unsolicited) to the user to report PVC status changes in a more timely fashion than waiting for the next Status Enquiry from the user.

The SyncLink adapter supports two PVC management protocols: ANSI T1.617 Annex D and ITU Q.922 Annex A. Most modern U.S. implementations for network switches and user equipment follow the T1.617 Annex D specification. Q.933 Annex A is used mostly in Europe and Japan.

The PVC management protocol is specified by the network provider at subscription time.


Adapter Switch and Jumper Settings

The SyncLink PCI adapter has no jumper or switch settings for configuring the resources used by the adapter. Adapter resources are automatically configured by the computer BIOS and the operating system. The adapter uses two I/O address ranges, two memory address ranges, and an interrupt.

The SyncLink ISA adapter has three resources that must be configured by properly setting the DIP switches and jumpers on the adapter.

DIP Switch S1

The DIP switch is located in the lower center of the adapter. The switch has 3 positions which determine which base I/O address the adapter uses:

Base I/O Address	Sw1 Pos1	Sw1 Pos 2	Sw1 Pos 3
100	OFF	OFF	OFF
110	OFF	OFF	ON
120	OFF	ON	OFF
200	OFF	ON	ON
210	ON	OFF	OFF
300	ON	OFF	ON
310	ON	ON	OFF
Disabled	ON	ON	ON

The SyncLink interrupt is set using the Jumper marked USC IRQ located at the bottom center of the adapter. The jumper block is a set of pins arranged 2 pins by 8 pins. To select a particular IRQ level look at the label above the jumper block. Place the jumper on the pair of pins below the desired IRQ level such that the jumper is vertically oriented as shown below:

Interrupt jumper setting for IRQ level 5.

The DMA Channel is set in a similar fashion as the IRQ level. The jumper blocks for the DMA settings are located in the lower left area of the adapter. Two jumpers must be positioned for the DMA Channel: DMA Request and DMA Acknowledge. Look at the label above the jumper blocks for the desired DMA channel. Place BOTH jumpers on the REQ and ACK block for the same DMA channel as shown below:

DMA Jumper settings for DMA Channel 3.


Warranty

This section describes the limited hardware warranty.

Limited Hardware Warranty

MicroGate Corporation warrants this hardware product to be in good working order for a period of one (1) year from the date of purchase by Buyer from MicroGate Corporation or an authorized MicroGate Corporation Reseller. Should the product fail to be in good working order at any time during this one year warranty period, MicroGate Corporation will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts or replacement products will be furnished on an exchange basis and will be either reconditioned or new at the discretion of MicroGate Corporation. Repaired or replacement units shall be warranted for the remainder of the original one year warranty period. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, misuse, abuse, or modifications which have not been made or authorized by MicroGate Corporation.

To validate this Limited Hardware Warranty, Buyer must complete and return the Limited Hardware Warranty Registration Form supplied by MicroGate Corporation within thirty (30) days of purchase.

Beyond the warranty period, MicroGate Corporation will repair or replace defective hardware products for a fixed price if defects are not due to accident, disaster, abuse, misuse, or modifications which have not been made or authorized by MicroGate Corporation.

If this product should require service, obtain a Return Material Authorization (RMA) number from MicroGate Corporation and return the product in its original shipping carton (or equivalent shipping container with the board protected by one inch non-static padding) to the address below, shipping prepaid, along with proof of purchase, a return address, a telephone contact, and an explanation of the suspected defect. You agree to insure the product or assume the risk of loss or damage in transit. C.O.D returns are not accepted.

MicroGate Corporation

9501 N. Capital of Texas Highway, Suite 105

Austin, Texas 78759

Attention: RMA #:________

There are no warranties, expressed or implied, including, but not limited to, those of merchantability and fitness for a particular purpose, which extend beyond the description and duration set forth herein.

MICROGATE CORPORATION'S SOLE OBLIGATION UNDER THIS WARRANTY IS LIMITED TO THE REPAIR OR REPLACEMENT OF A DEFECTIVE PRODUCT AND MICROGATE CORPORATION SHALL NOT, IN ANY EVENT, BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND RESULTING FROM THE USE OR POSSESSION OF THIS PRODUCT.

THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE.

Limited Hardware Warranty Registration

|	Please complete and mail this form to validate your MicroGate Corporation Limited Hardware Warranty.

|

Mail to:	MicroGate Corporation

|	9501 N. Capital of Texas Highway

Suite 105

|	Austin, Texas 78759

Attn: Warranty Registration

|

Date:___________________

|

|	Name:______________________________________________________

|

Phone: ____________________________________________________

|

|	Title: ____________________________________________________

|

Organization: _____________________________________________

|

|	Street Address: ___________________________________________

|	___________________________________________________________

|

City/State/Zip: ___________________________________________

|

|	Product Purchased: ________________________________________

|

Hardware S/Ns: ____________________________________________

|

|	___________________________________________________________

|

Purchased from: ___________________________________________

|

|	___________________________________________________________

|

___________________________________________________________

|

|	Date Purchased: ___________________

Customer Support

If you need to contact customer support, please call MicroGate at (512)345-7796 weekdays between the hours of 8:00 A.M. and 5:00 P.M. CST, except holidays.

Support may also be obtained by email, support@microgate.com.


Data Link Connection Identifier (DLCI)

The DLCI is a number from 16 to 1008 that identifies a virtual circuit that connects two endpoints. The DLCI is assigned by the network provider at subscription time. This number is effectively the frame relay ‘address’ of the remote computer.


Adapter Property Sheet

Follow this procedure to display the adapter property sheet:

Right click on My Computer on the desktop.

Select the Properties menu item from the popup menu.

Click on the Hardware tab on the property sheet.

Click on the Device Manager button on the Hardware property page.

Expand the Network Adapters item in the right side of the Device Manager window.

Right click on the SyncLink Frame Relay Adapter item.

Select the Properties menu item from the popup menu.


Resources

The Resources property page displays the computer resources used by the adapter. SyncLink PCI adapter resources are automatically assigned and cannot be changed by the user. SyncLink ISA adapter resources must be manually assigned by the user.

WARNING

Computers that have both ISA/EISA and PCI buses may reserve interrupt levels for either the ISA or PCI buses. This selection is often configured in the CMOS setup that is available when the computer is turned on. Be sure that at least one free interrupt level is available to the PCI bus for use by the SyncLink PCI adapter. Consult your computer documentation for details about the CMOS setup procedures.

WARNING

The Base I/O Address, Interrupt Level, and DMA Channel settings of the SyncLink ISA adapter MUST match the actual hardware settings (DIP switches and jumpers) for the adapter. Each of these settings MUST NOT conflict with the settings of other adapters or devices in the computer!


Verify PVC Connection
Verify PVC Connections

Run the MicroGate SyncLink Frame Relay Monitor program by typing MGFRMON at a command prompt. The program displays the status of the adapter and each virtual circuit. The left side of the monitor window is a tree control containing a list of the installed adapters, the logical adapters assigned to each adapter, and the virtual circuits assigned to each logical adapter. Click on an item to view it’s status in the right side of the window. Consult the online help for more information.

Verify that PVC management protocol frames are being transferred between the SyncLink adapter and the frame relay network. Left click on the physical adapter item in the left side of the monitor window. The adapter status is displayed in the right side of the monitor window. Look at the status item titled Status ENQ Messages Sent and Status Messages Received. Every 10 seconds the status ENQ message count should increment. Shortly after this the Status Message Received count should increment. If they are not incrementing, there is probably a problem with the connection between the SyncLink adapter and the CSU/DSU or the CSU/DSU is not configured or operating properly. Check all cable connections and ensure all devices are properly powered on and configured. Verify that the correct cables are being used.

Verify that both locations report the PVC as active. Left click on the PVC item in the left side of the monitor window. The status for the PVC will be displayed in the right side of the monitor window. Look at the entry titled Status. The status for a PVC is one of three possible values: Deleted, Inactive, and Active.

When a PVC is listed as deleted, the frame relay network has no information about the PVC. This is usually caused by an incorrectly specified DLCI for the PVC in the software configuration. Verify that the specified DLCI matches the DLCI agreed upon with the network provider at subscription time. Another possible problem is a mismatch of the PVC management protocol.

When a PVC is listed as inactive, then the frame relay network recognizes that the PVC exists but is reporting that it is not available for use. The most likely cause is an inactive remote site. Verify that the remote computer is on and properly connected to the frame relay network.

When a PVC is listed as active then the DLCI is correctly specified and the PVC is ready to transfer data. When both sides of a PVC report the PVC as active, proceed to the next step - verifying the network connection.